Skip to main content

ORSANCO Meeting Notes 7/13/2023

  • Previous money (EPA) dried up 3 months ago.
  • 12k set aside for maintanence. Available now, starting July 1.
  • Checking flows, keeping up with any NWS changes.
  • Interacting with Brian NOAA making sure flows are inserting.
  • Currently site is based on 10 year old technology (with some minor upgrades), but it could use some future proofing with modern technologies.
  • I would be interested in exploring blazor sometime. Not sure if it fits with RSMS or really any of our work.
  • We'll want to save all the old runs/scenarios from existing server(s).
  • They usually just run with default settings, not tweaking anything except the basic fields like number of stations.
  • Set aside $2400 for the initial cutover. Remaining $9600 on a monthly basis as support is needed, maybe $800/mo for hosting fee (hosting plus support). Or $800 hosting + x hours support.
  • They've talked to Jim Goodrich and he's interested in talking to his people about upgrading the model, based on ORSANCO's monitoring data. Backcasting related to that, some other advanced features.
  • Brian Astifan is in Wilmington, OH. Ohio River Forecast Center.
  • Next HECRAS modelers meeting? With Charles at USACE.
  • People at Ohio EPA: Amy Cly (drinking water), Tiffany Cadillac (surface water, but new role), Amy Vogel (head). Not sure about these names...
  • Could upgrade so model uses 1 hour data instead of 6 hour data, or we take the hourly data and generate the 6 hour from it (use ORSANCO Flows data instead of RSMS data). Use cases for both, maybe switch in the UI?
  • Two big spills with good data. East Pallestine and the 2017 Louisville Christmas spill.
  • They've received money from USACE in the past but not for anything related to this kind of work (RSMS, Flows?)
  • Community model will change eventually, RSMS needs upgraded, how do we bring together the resources needed.
  • Another update spoken with Jim Goodrich - the decay coefficient is in there, but historically they're more interested in time of travel and less in concentration. Talked about contaminant libraries as possible upgrade.
  • Adam Davis at NOAA (SSC Senior Science Coordinator) has completely different model (NOAA specific model), when Coast Guard is the lead. How the lead agency is determined? Commercial Vessel is coast guard. Offloading facilities up to first valve is also Coast Guard. Navigable waterways and facilities under jurisdiction of Coast Guard. Past first valve it's EPA or on non-navigable waterways.
  • Their model is good for oil spills. Deals with wind speed, air temperatures, losses from volatization.
  • GNOME Suite, ADIOS, TAP all models from NOAA.
  • https://response.restoration.noaa.gov/gnomesuite
  • https://gnome.orr.noaa.gov/
  • This all seems to be primarily used in oceanic scenarios.

  • We'll check with our EPA contacts regarding any RSMS support.
  • Reach out to ___ about community model updates schedule.

  • Some background info needs to be added to the Ohio River Flows site. We will need to work with Brian to get that information together.
  • They haven't even discussed the auth aspect of this site/data. They want it to be made available to more agencies, but details aren't finalized yet.
  • A few users will be fine. More than that, maybe 10 or more concurrent users, will need to start upgrading the resources.
  • Various state grants (water quality planning grants?) would potentially be used to fund this project.

  • NEED TO VERIFY FLOW DOWNLOADER, FLOWS HAVEN'T PROCESSED SINCE 7/6/23

  • Provide them with a quote on the Spill Model. Labor + hosting.
  • Provide them with a quote on the Flows Database/site. Hosting (Azure, certs, domain) and labor.

  • Get them temporary pricing for as-is.
  • Additional quote for more changes req, i.e. moving resources to ORSANCO Azure account.

  • On the spills one, staff time
  • Flows is some staff time (NOAA server etc.) but mostly hosting.

  • Single page quote for each, that would be Adendum A for a professional services agreement.
  • Come up with some number of hours support per week (staff hours) which would be in addition to the hosting/static costs.
  • Estimate how much time we spent on Flows and RSMS per month as "average" support. Look back at timesheets or topsheets.